home *** CD-ROM | disk | FTP | other *** search
/ IRIX Installation Tools & Overlays 2002 May / SGI IRIX Installation Tools & Overlays 2002 May - Disc 3.iso / relnotes / divo / ch3.z / ch3
Text File  |  2002-04-11  |  16KB  |  265 lines

  1.  
  2.  
  3.  
  4.                                   - 1 -
  5.  
  6.  
  7.  
  8.        3.  _C_o_n_f_i_g_u_r_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n
  9.  
  10.  
  11.  
  12.        3.1  _D_e_v_i_c_e__n_u_m_b_e_r_i_n_g
  13.  
  14.  
  15.        Multiple DIVO and/or DIVO-DVC boards may be installed in one
  16.        system. Each DIVO/DIVO-DVC board is assigned a device name
  17.        and number by the video daemon (videod), a part of the SGI
  18.        Video Library (VL).  These names are visible under the
  19.        "Device" menu in the _v_i_d_e_o_p_a_n_e_l (a.k.a. _v_c_p) utility. Also,
  20.        the names and corresponding numbers are displayed by running
  21.        the _v_l_i_n_f_o command-line utility.  For example, if a system
  22.        has three DIVO boards and one DIVO-DVC board, they are named
  23.        DIVO_1, DIVO_2, DIVO_3, and DIVO_DVC_4.  They may be
  24.        numbered 0, 1, 2, and 3, respectively. These latter numbers
  25.        correspond to the indices of the VLDevList array returned by
  26.        the _v_l_G_e_t_D_e_v_i_c_e_L_i_s_t(_3) Video Library function.  However, if
  27.        another type of video card besides DIVO and DIVO-DVC is
  28.        installed in the same system, the mapping between name and
  29.        number may change, because the other board would be
  30.        allocated some numbers.
  31.  
  32.        The numbering of Audio Library devices matches the VL name
  33.        (e.g., DIVO_1 in AL is the same board as DIVO_1 in VL.)  The
  34.        system administrator has control over the assignment of VL
  35.        device names of the DIVO/DIVO-DVC boards in the system, but
  36.        little control over the VL device number.  Device number
  37.        assignment occurs in two phases: first, DIVO board numbers
  38.        are initially assigned by the _i_o_c_o_n_f_i_g(_1) IRIX utility,
  39.        which takes into account the module and slot into which the
  40.        DIVO/DIVO-DVC boards are installed.  By editing
  41.        /_e_t_c/_i_o_c_o_n_f_i_g._c_o_n_f, this assignment can be modified.
  42.        Second, the VL sorts the ioconfig numbers and assigns VL
  43.        device numbers in ascending, consecutive order (this second
  44.        phase is necessary because the VL and many VL programs were
  45.        written assuming VL devices are numbered consecutively
  46.        starting from zero.  Numbers assigned by _i_o_c_o_n_f_i_g are not
  47.        necessarily so.)  The device name assigned by VL is "DIVO_n"
  48.        or "DIVO_DVC_n", where "n" is the IRIX unit number assigned
  49.        by ioconfig.
  50.  
  51.  
  52.        3.2  _H_a_r_d_w_a_r_e__i_n_v_e_n_t_o_r_y
  53.  
  54.  
  55.        For each DIVO or DIVO-DVC installed, a line is displayed by
  56.        _h_i_n_v(_1).  No distinction between a DIVO or DIVO-DVC is made
  57.        here.  For example,
  58.  
  59.  
  60.  
  61.  
  62.  
  63.  
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70.                                   - 2 -
  71.  
  72.  
  73.  
  74.        %%%% hhhhiiiinnnnvvvv
  75.        DDDDIIIIVVVVOOOO VVVViiiiddddeeeeoooo:::: ccccoooonnnnttttrrrroooolllllllleeeerrrr 3333 uuuunnnniiiitttt 3333 ssssttttaaaatttteeee 0000
  76.        DDDDIIIIVVVVOOOO VVVViiiiddddeeeeoooo:::: ccccoooonnnnttttrrrroooolllllllleeeerrrr 1111 uuuunnnniiiitttt 1111 ssssttttaaaatttteeee 0000
  77.        DDDDIIIIVVVVOOOO VVVViiiiddddeeeeoooo:::: ccccoooonnnnttttrrrroooolllllllleeeerrrr 2222 uuuunnnniiiitttt 2222 ssssttttaaaatttteeee 0000
  78.        DDDDIIIIVVVVOOOO VVVViiiiddddeeeeoooo:::: ccccoooonnnnttttrrrroooolllllllleeeerrrr 0000 uuuunnnniiiitttt 0000 ssssttttaaaatttteeee 0000
  79.  
  80.        The ccccoooonnnnttttrrrroooolllllllleeeerrrr number is the number assigned by _i_o_c_o_n_f_i_g(_1)
  81.        utility and referenced in the /_e_t_c/_i_o_c_o_n_f_i_g._c_o_n_f database.
  82.        The uuuunnnniiiitttt number is the VL device number assigned by videod.
  83.        Note that _u_n_i_t will be zero for all DIVO/DIVO-DVC boards
  84.        until videod runs for the first time.  Note also that the
  85.        DIVO or DIVO-DVC software must be installed and running for
  86.        _h_i_n_v to display anything about DIVO or DIVO-DVC.  The serial
  87.        numbers of all DIVO/DIVO-DVC boards (and other boards) in
  88.        the system, along with their physical location (by module
  89.        number and I/O slot number) can be displayed (note that the
  90.        first three devices are DIVO boards and the last device is a
  91.        DIVO-DVC, which is a DIVO with two attached daughtercards
  92.        named DVCPRO_CODEC):
  93.  
  94.        %%%% hhhhiiiinnnnvvvv ----mmmmvvvv
  95.        LLLLooooccccaaaattttiiiioooonnnn:::: ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo2222////ddddiiiivvvvoooo
  96.                    DDDDIIIIVVVVOOOO BBBBooooaaaarrrrdddd:::: bbbbaaaarrrrccccooooddddeeee DDDDPPPPWWWW000000002222     ppppaaaarrrrtttt 000033330000----1111000044446666----000000002222 rrrreeeevvvv  GGGG
  97.        LLLLooooccccaaaattttiiiioooonnnn:::: ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo6666////ddddiiiivvvvoooo
  98.                    DDDDIIIIVVVVOOOO BBBBooooaaaarrrrdddd:::: bbbbaaaarrrrccccooooddddeeee DDDDAAAARRRR000055556666     ppppaaaarrrrtttt 000033330000----1111000044446666----000000002222 rrrreeeevvvv  GGGG
  99.        LLLLooooccccaaaattttiiiioooonnnn:::: ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo5555////ddddiiiivvvvoooo
  100.                    DDDDIIIIVVVVOOOO BBBBooooaaaarrrrdddd:::: bbbbaaaarrrrccccooooddddeeee DDDDAAAARRRR000055559999     ppppaaaarrrrtttt 000033330000----1111000044446666----000000002222 rrrreeeevvvv  GGGG
  101.        LLLLooooccccaaaattttiiiioooonnnn:::: ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo3333////ddddiiiivvvvoooo
  102.            DDDDVVVVCCCCPPPPRRRROOOO____CCCCOOOODDDDEEEECCCC BBBBooooaaaarrrrdddd:::: bbbbaaaarrrrccccooooddddeeee FFFFXXXXXXXX111100005555     ppppaaaarrrrtttt 000033330000----1111333388888888----000000001111 rrrreeeevvvv  AAAA
  103.                    DDDDIIIIVVVVOOOO BBBBooooaaaarrrrdddd:::: bbbbaaaarrrrccccooooddddeeee FFFFXXXXXXXX555566662222     ppppaaaarrrrtttt 000033330000----1111333388887777----000000001111 rrrreeeevvvv  AAAA
  104.            DDDDVVVVCCCCPPPPRRRROOOO____CCCCOOOODDDDEEEECCCC BBBBooooaaaarrrrdddd:::: bbbbaaaarrrrccccooooddddeeee FFFFXXXXXXXX000077770000     ppppaaaarrrrtttt 000033330000----1111333388888888----000000001111 rrrreeeevvvv  AAAA
  105.  
  106.        A tool _d_i_v_o_h_i_n_v is included with the DIVO software that
  107.        gathers this information and associates it with VL device
  108.        number, for convenience:
  109.  
  110.        %%%% ////uuuussssrrrr////ddddmmmmeeeeddddiiiiaaaa////bbbbiiiinnnn////DDDDIIIIVVVVOOOO////ddddiiiivvvvoooohhhhiiiinnnnvvvv
  111.        ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo2222////ddddiiiivvvvoooo
  112.                DDDDIIIIVVVVOOOO ((((ppppaaaarrrrtttt nnnnuuuummmmbbbbeeeerrrr 000033330000----1111000044446666----000000002222 GGGG)))),,,, sssseeeerrrriiiiaaaallll nnnnuuuummmmbbbbeeeerrrr DDDDPPPPWWWW000000002222
  113.                VVVVLLLL ddddeeeevvvviiiicccceeee 3333 ((((nnnnaaaammmmeeee DDDDIIIIVVVVOOOO____3333)))),,,, AAAALLLL ssssuuuubbbbssssyyyysssstttteeeemmmm DDDDIIIIVVVVOOOO____3333
  114.                IIIIRRRRIIIIXXXX nnnnuuuummmmbbbbeeeerrrr 3333
  115.        ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo3333////ddddiiiivvvvoooo
  116.                DDDDVVVVCCCCPPPPRRRROOOO____CCCCOOOODDDDEEEECCCC ((((ppppaaaarrrrtttt nnnnuuuummmmbbbbeeeerrrr 000033330000----1111333388888888----000000001111 AAAA)))),,,, sssseeeerrrriiiiaaaallll nnnnuuuummmmbbbbeeeerrrr FFFFXXXXXXXX111100005555
  117.                DDDDIIIIVVVVOOOO ((((ppppaaaarrrrtttt nnnnuuuummmmbbbbeeeerrrr 000033330000----1111333388887777----000000001111 AAAA)))),,,, sssseeeerrrriiiiaaaallll nnnnuuuummmmbbbbeeeerrrr FFFFXXXXXXXX555566662222
  118.                DDDDVVVVCCCCPPPPRRRROOOO____CCCCOOOODDDDEEEECCCC ((((ppppaaaarrrrtttt nnnnuuuummmmbbbbeeeerrrr 000033330000----1111333388888888----000000001111 AAAA)))),,,, sssseeeerrrriiiiaaaallll nnnnuuuummmmbbbbeeeerrrr FFFFXXXXXXXX000077770000
  119.                VVVVLLLL ddddeeeevvvviiiicccceeee 0000 ((((nnnnaaaammmmeeee DDDDIIIIVVVVOOOO____DDDDVVVVCCCC____0000)))),,,, AAAALLLL ssssuuuubbbbssssyyyysssstttteeeemmmm DDDDIIIIVVVVOOOO____DDDDVVVVCCCC____0000
  120.                IIIIRRRRIIIIXXXX nnnnuuuummmmbbbbeeeerrrr 0000
  121.        ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo5555////ddddiiiivvvvoooo
  122.                DDDDIIIIVVVVOOOO ((((ppppaaaarrrrtttt nnnnuuuummmmbbbbeeeerrrr 000033330000----1111000044446666----000000002222 GGGG)))),,,, sssseeeerrrriiiiaaaallll nnnnuuuummmmbbbbeeeerrrr DDDDAAAARRRR000055559999
  123.                VVVVLLLL ddddeeeevvvviiiicccceeee 2222 ((((nnnnaaaammmmeeee DDDDIIIIVVVVOOOO____2222)))),,,, AAAALLLL ssssuuuubbbbssssyyyysssstttteeeemmmm DDDDIIIIVVVVOOOO____2222
  124.                IIIIRRRRIIIIXXXX nnnnuuuummmmbbbbeeeerrrr 2222
  125.  
  126.  
  127.  
  128.  
  129.  
  130.  
  131.  
  132.  
  133.  
  134.  
  135.  
  136.                                   - 3 -
  137.  
  138.  
  139.  
  140.        ////hhhhwwww////mmmmoooodddduuuulllleeee////1111////ssssllllooootttt////iiiioooo6666////ddddiiiivvvvoooo
  141.                DDDDIIIIVVVVOOOO ((((ppppaaaarrrrtttt nnnnuuuummmmbbbbeeeerrrr 000033330000----1111000044446666----000000002222 GGGG)))),,,, sssseeeerrrriiiiaaaallll nnnnuuuummmmbbbbeeeerrrr DDDDAAAARRRR000055556666
  142.                VVVVLLLL ddddeeeevvvviiiicccceeee 1111 ((((nnnnaaaammmmeeee DDDDIIIIVVVVOOOO____1111)))),,,, AAAALLLL ssssuuuubbbbssssyyyysssstttteeeemmmm DDDDIIIIVVVVOOOO____1111
  143.                IIIIRRRRIIIIXXXX nnnnuuuummmmbbbbeeeerrrr 1111
  144.        %%%%
  145.  
  146.        3.3  _G_P_I__c_o_n_f_i_g_u_r_a_t_i_o_n
  147.  
  148.  
  149.        The four GPI input receivers can each be configured into one
  150.        of two modes (current sense or switch closure) via jumpers
  151.        on the DIVO circuit board.  This configuration is the
  152.        responsibility of the SGI System Engineer installing the
  153.        board, and is explained in detail in the _D_I_V_O _I_n_s_t_a_l_l_a_t_i_o_n
  154.        _G_u_i_d_e.  DIVO and DIVO-DVC boards are not customer-
  155.        installable.
  156.  
  157.  
  158.        3.4  _I_n_i_t_i_a_l_i_z_a_t_i_o_n
  159.  
  160.  
  161.        The DIVO/DIVO-DVC Video subsystems are initialized by the
  162.        video daemon, which is normally started at boot time If not
  163.        started at boot time, the video daemon is started when the
  164.        first program that uses the VL is executed.  The
  165.        initialization process normally takes about 7-8 seconds per
  166.        board.  The advantage to starting videod at boot time is
  167.        that VL programs start much faster.  The disadvantages are
  168.        that system boot-up time increases, and that videod starts
  169.        and runs, consuming some CPU and memory resources, even
  170.        before DIVO/DIVO-DVC is used.  To disable videod from
  171.        automatically starting, use the IRIX utility _c_h_k_c_o_n_f_i_g(_1),
  172.        as root, to turn the _v_i_d_e_o_d and _i_n_i_t_d_i_v_o flags off:
  173.  
  174.                cccchhhhkkkkccccoooonnnnffffiiiigggg vvvviiiiddddeeeeoooodddd ooooffffffff
  175.                cccchhhhkkkkccccoooonnnnffffiiiigggg iiiinnnniiiittttddddiiiivvvvoooo ooooffffffff
  176.  
  177.        To reenable,
  178.  
  179.                cccchhhhkkkkccccoooonnnnffffiiiigggg iiiinnnniiiittttddddiiiivvvvoooo oooonnnn
  180.  
  181.        While initialization normally takes 7-8 seconds per
  182.        DIVO/DIVO-DVC board, it can in some cases take much longer.
  183.        If the DIVO/DIVO-DVC software is upgraded, a new DIVO or
  184.        DIVO-DVC board is installed, or a DIVO/DIVO-DVC board is
  185.        replaced, videod may have to "reflash" (reprogram) the
  186.        firmware onto the board the first time videod runs after the
  187.        upgrade.  This process takes about 45 seconds (for DIVO) to
  188.        60 seconds (for DIVO-DVC) per board, during which VL
  189.        programs appears to freeze.  Fortunately, this reflashing
  190.        process occurs rarely.
  191.  
  192.  
  193.  
  194.  
  195.  
  196.  
  197.  
  198.  
  199.  
  200.  
  201.  
  202.                                   - 4 -
  203.  
  204.  
  205.  
  206.  
  207.  
  208.  
  209.  
  210.  
  211.  
  212.  
  213.  
  214.  
  215.  
  216.  
  217.  
  218.  
  219.  
  220.  
  221.  
  222.  
  223.  
  224.  
  225.  
  226.  
  227.  
  228.  
  229.  
  230.  
  231.  
  232.  
  233.  
  234.  
  235.  
  236.  
  237.  
  238.  
  239.  
  240.  
  241.  
  242.  
  243.  
  244.  
  245.  
  246.  
  247.  
  248.  
  249.  
  250.  
  251.  
  252.  
  253.  
  254.  
  255.  
  256.  
  257.  
  258.  
  259.  
  260.  
  261.  
  262.  
  263.  
  264.  
  265.